Skip to content

gh-79009: sqlite3.iterdump now correctly handles tables with autoincrement#9621

Merged
erlend-aasland merged 15 commits intopython:mainfrom
itssme:fix-issue-34828
Jun 19, 2022
Merged

gh-79009: sqlite3.iterdump now correctly handles tables with autoincrement#9621
erlend-aasland merged 15 commits intopython:mainfrom
itssme:fix-issue-34828

Conversation

@itssme
Copy link
Contributor

@itssme itssme commented Sep 28, 2018

The iterdump command in Lib/sqlite3/dump.py assumed that the table "sqlite_sequence" already exists. When this was not the case and exception was thrown.

Changes:

  • Sqlite3 iterdump now deletes and recreates the "sqlite_sequence" table at the end of the transaction (Just like the sqlite3 command ".dump" does)
  • Added two new test for the iterdump command

Resolves gh-79009

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sqlite.iterdump does not work for (most) databases with autoincrement

6 participants